[19.0][MIG] edi_core_oca #215
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* auto btns on/off flag per exchange type * offer hook to customize how btns are rendered * improve UI
Raise specific error when exchange type is not found.
To be used to track references on exchanged related records.
Handy method to validate core actions of the edi framework.
Kewyord params were not propagated.
Propagate custom kw args to event handlers.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-15.0/edi-15.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-15-0/edi-15-0-edi_oca/
You can now track the original exchange record that originated the document in the 1st place.
Ease finding which type the current one is an ack for.
You can produce or receive more than one ack for a given exchange. If that's the case, make sure only the newest is considered.
In case exchange_on is the same, use ID to get the latest on top.
Skip 'output_sent' records by default. Reason: most of the times when a message is sent out you don't care about its state anymore. Any subsequent update from outside should come with a new input record instead. Yet, if for any reason this feature is required you can still enable it by passing 'skip_sent=False'.
Contributor
So far the file could be edited in any state and w/o any trace of editing. This change brings: * the file is frozen if it has been already processed or sent * if you really need to change it you can force this by assigning the group ``group_edi_override_exchange_file_content`` to the user * updates to the file are now tracked via checksum changes
model.model few lines below will trigger an access error w/o this change.
etobella
force-pushed
the
19.0-mig-edi_core_oca
branch
2 times, most recently
from
0e6d581 to
8dced0b
Compare
Member
Author
|
@simahawk WDYT? |
Member
Author
|
@simahawk is it ok to you to proceed with merge? |
There were 3 ways to access the related record. Now there's only 2 but we still display the warning if the relation with the main record is broken.
etobella
force-pushed
the
19.0-mig-edi_core_oca
branch
from
8dced0b to
efe076e
Compare
simahawk
approved these changes
Feb 2, 2026
Member
Author
|
/ocabot migration edi_core_oca |
Member
Author
|
/ocabot merge nobump |
Contributor
|
This PR looks fantastic, let's merge it! |
Contributor
|
This PR has the |
Contributor
|
Congratulations, your PR was merged at d22e572. Thanks a lot for contributing to OCA. ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Done the history rewritting for not losing the commits from edi_oca and map them in edi_core_oca (Since the split, obviously).
I added JS tests 😉
I avoided the use of odoo_test_helper